Route /api/assistant to dt-web in the ingress #125
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The ingress only sends /api/auth, /api/mcp, /api/dt and /api/tools to dt-web. All other /api paths go to FastAPI, so the assistant's chat endpoint (POST /api/assistant) got a 404 from dt-api in production. This adds /api/assistant to dt-web, next to the other Next.js API prefixes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign in
to join this conversation on GitHub.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In production, the
dt-nanohub-servicesingress sends only/api/auth,/api/mcp,/api/dtand/api/toolsto dt-web; every other/apipath goes to FastAPI. The assistant added in #124 posts to/api/assistant, so that request went to dt-api and got a 404, and the chat failed.This adds
/api/assistant(Prefix) →dt-web:3000togeddes/k8s/04-ingress.yaml, next to the other Next.js API prefixes./api/assistant, so nothing is shadowed.proxy.tsauth (401 without a session), and the route handler checks the session itself.The live ingress gets the same rule through a
kubectl patchthat adds just this path, so the file matches the cluster.Codex review: APPROVE.
🤖 Generated with Claude Code